feat(container)!: Update image docker.dragonflydb.io/dragonflydb/dragonfly ( v1.38.1 → v2.0.0 ) - #1849
Open
chaplain-grimaldus[bot] wants to merge 1 commit into
Conversation
…onfly ( v1.38.1 → v2.0.0 )
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.38.1→v2.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
dragonflydb/dragonfly (docker.dragonflydb.io/dragonflydb/dragonfly)
v2.0.0Compare Source
Dragonfly v2.0.0
We have been waiting three years to bump the major version.
While this specific release does not add new major features by itself, it marks a significant milestone in our maturity, performance, and production readiness.
Dragonfly v2.0.0 expands Redis and Valkey compatibility with Valkey 9 RDB loading, GEOSEARCHSTORE, and improved replication backlog controls. Performance work reduces connection-processing and memory-accounting overhead while adding tighter controls for defragmentation and buffer retention. Tiered storage, cluster migration, streams, compressed lists, and RESP3 behavior received substantial correctness improvements. This release also strengthens RESTORE validation against malformed or incompatible payloads.
Highlights
Commands
MEMORY DEFRAGMENT-SEGMENTS [threshold]to reclaim sparsely used DashTable pages and report page usage. (#7995)Performance
Replication
Bug fixes
SLOWLOG GETnow returns 10 entries by default while preserving explicit counts and-1. (#8248)redis-cli --pipesentinel timeouts. (#8244)SORT LIMITrange overflow near 32-bit limits. (#8212)<index>: no such indexFT.INFO error. (#8199)SORT ... STOREdelete the destination and return0when the source is missing. (#8190)used_memory_peak_rssreport peak resident memory. (#8143)ZADD GTandZADD LTfor skiplist-encoded sorted sets. (#8091)tls_bytesaccounting. (#8043)expired_keys_totalandevicted_keys_total, including zero values. (#8052)Huge thanks to all the contributors! ❤️
New Contributors
What's Changed
Full Changelog: dragonflydb/dragonfly@v1.40.0...v2.0.0
v1.40.2Compare Source
What's Changed
Tiered storage (disk offload)
tiered_max_pending_bytescap that covers both in-flight reads and writes, and export read/write/total usage as metrics.tiered_serialization_inflight_bytes_cap— snapshot serialization now throttles/waits when there are too many outstanding tiered reads, preventing unbounded memory growth from delayed entries during snapshotting.TraverseBySegmentOrder(same class of fix asDeleteExpiredStepin #8129), preventing entries from being skipped or revisited when the table resizes mid-scan; also exports additional tiering metrics/settings.INFO.tiered_repack_scan_budget_us=0).Replication / journal
DeleteExpiredSteptraversal withTraverseBySegmentOrder(#8129)EXPIREwrites that skip serialization.FLUSHSLOTSfrom inside the flush transaction, avoiding replication inconsistency during slot migration (#8061, backports #8032)Protocol
VALUEreply, overflowing the reply buffer.Advisory: it is advised to upgrade to this release due to the correctness bug with journaling #8157
v1.40.1Compare Source
This is a patch release.
What's Changed
AUTH,SELECT,HELLO,CLIENT, orRESETnow observe the updated connection state instead of stale authentication, database, or RESP protocol state (#8016).Full Changelog: v1.40.0...v1.40.1
v1.40.0Compare Source
Dragonfly v1.40.0
This is one of our biggest releases yet—both in terms of feature quality, total contributions, and the highest number of external contributors in the last two years.
This release delivers major new functionality alongside a large body of correctness and stability fixes for tiered storage, replication, pub/sub, and the experimental V2 I/O loop.
We added a new data type: Cuckoo Filters (CF.RESERVE, CF.ADD/ADDNX, CF.EXISTS/MEXISTS, CF.INSERT/INSERTNX, CF.INFO/COUNT/DEL/COMPACT, and RDB persistence). This brings Dragonfly to parity with RedisBloom's probabilistic structures alongside expanded Bloom filter (BF.INFO) and HyperLogLog support.
Vector search gains native-width storage across all vector dtypes, EPSILON-tuned HNSW range queries, and EF_RUNTIME control. Meanwhile, a long list of fixes hardens tiered-storage interactions with strings, hashes, lists, bitops, and HLL commands, in addition to several replication-consistency fixes around lazy TTL expiry. Performance work includes lazy lock-table registration, zero-copy GET, and replica-side command batching.
Highlights
Configuration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate CLI.